Silk Road forums
Support => Technical support => Topic started by: performance on June 27, 2011, 06:43 pm
-
I liked the old forum better. Posts appeared immediately, and it was much faster.
This new one, quite frankly STINKS! I don't know how else to put it. No matter how much I refresh, or log in and out, my posts don't show up. I couldn't even add a simple attachment, and I had to cancel my post because it wouldn't let me remove the attachment that was too large.
There's no BBCode, etc...
why did we go with such a weak software package?
-
Ctr+F5. SMF isn't bad forum software, it's actually quite good, it just appears to have a problem with TOR and caching.
-
@g4bb3r can you confirm it's not <shift> F5 ? us old guys learn slow...
-
if the forum software stinks, has anyone tried to double vac seal it so the feds can't smell it?
-
if the forum software stinks, has anyone tried to double vac seal it so the feds can't smell it?
You fuckin poptart, that's hilarious!
Also crtl + F5 fixes everything, everytime like g4bb3r said.
-
Sorry OP but I don't know what you're saying because your post isn't coming up.
-
user error ? :P
-
It is ctrl + F5. I suspect people using tor-button are not experiencing said problem, but people using the Tor Browser Bundle are.
Peace,
DigitalAlch
(Suck it up, the trails are tough we are pioneers - oh and its just two buttons :D )
-
It is ctrl + F5. I suspect people using tor-button are not experiencing said problem, but people using the Tor Browser Bundle are.
Peace,
DigitalAlch
(Suck it up, the trails are tough we are pioneers - oh and its just two buttons :D )
I use the bundle and its fine. Maybe some are using an old browser bundle?
-
Ctr+F5. SMF isn't bad forum software, it's actually quite good, it just appears to have a problem with TOR and caching.
Yeah, I'm glad you pointed it out: it did seem to be caching...as if I'd totally log out, and start back up, it was speedy again...seems to get jammed up after about 20 pages or so...for a while I'd set up Chrome rather than iceWeasel, to use TOR, and it was *way* faster, and worked fine, even in TOR...but I wasn't as familiar with the security protection, and went back to iceweasel which, like I said, after loading around 20 pages or so, just gets *all* bogged down...like being back in dialup ha ha...gotta have a book to read, or a non-tor browser running so I can watch netflix while I'm waiting ;)
-
Control F5 finally worked for me.
-
I found this and some other stuff here that seemed to have sped me up quite a bit:
(from https://trac.torproject.org/projects/tor/wiki/doc/FireFoxTorPerf)
There was other stuff, but I got remarkable improvement from just changing these things:
Procedure 1 ΒΆ
First, open Firefox's advanced settings menu by running about:config from the address bar. Upon entering this address, you will see a long list of internal settings. Modify the following ones and set them to the suggested values shown here for maximum performance:
network.http.keep-alive.timeout:600 (300ms default is OK usually, but 600 is better.)
network.http.max-persistent-connections-per-proxy:16 (Default is 4)
network.http.pipelining:true (Default- false. Some old HTTP/1.0 servers can't handle it.)
network.http.pipelining.maxrequests:8 (No default)
network.http.proxy.keep-alive:true (Default- true, but double check)
network.http.proxy.pipelining:true (Default- false) - See NOTE1 below.
Afterwards, just restart the browser and experience the difference! For some automated additional performance hacks, check out the FasterFox extension. You also can do the same tweaks manually with the help of this page.
NOTE1: Proxy pipelining may not be well supported by Privoxy. For this reason, you may want to install Polipo and use that instead of Privoxy to get the performance benefits of pipelining. If you use Torbutton (which you should, if you want any anonymity at all), all of the Tor-relevant privacy scrubbing features of Privoxy are no longer necessary.
NOTE2: Do not use page prefetching. Disable this if it is enabled. Prefetching is a speculative feature, which assumes that you will read the pages referenced by the links in the current page you are viewing. This places undue load on the Tor network and clog your circuits with unnecessary traffic. Its unlikely you will read all the pages referenced by the current page, especially in the case of search engines results.